Improved field number type checking; correct bad usage detected #423
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
64-bit development found an instance of IsSet( record-member) where IsSet( record-member-field-number) was intended.
This PR includes several changes to field status access and testing functions to check that the fn (field number) is an integer. With this, the original offending error was detected along with several more. All have been fixed.
A more robust fix would be to define a type for field number. An issue has been added.
No results changes. No regression test changes. No documentation changes.